HTTPBodyEncoding error for J2EEProxy architecture

Relevant for

Java Servlet Architecture (J2EEProxy) - Websydian version 6.0 and 6.1

This is relevant for applications, where the Dispatcher inherits from WSYBASE/J2eeEventDispatcher.

This is not relevant for WebsydianExpress applications.

Symptoms

When you have deployed the servlet to the servlet engine (e.g. Tomcat or Websphere) and call the application, no page is shown and the following text is written to stdout of the servlet engine:

[Websydian: 24/08/11 11:30:33] No encoding set for translating request. Check value of HTTPBodyEncoding

For Tomcat, this text will be found in the stdout_[date].log file in the logs folder used by Tomcat.

Cause

In the obusr property file, you can specify a property: HTML.HTTP_BODY_ENCODING, which is used to determine the character encoding used for the response sent to the browser when no encoding has been specified in the request (e.g. for all GET requests).

This information was not handled correctly by the DWA runtime in the J2EE architecture, so the application was not able to determine the default encoding for GET requests.

Solution

Download and deploy the updated versions the WsydDwa21.jar and WsydUtil.jar files.